Skip to content

Conversation

@frantic
Copy link
Contributor

@frantic frantic commented Aug 20, 2013

I think README file should specify that in order to use builtin version of React user has to add a line to config file.

After installing the gem I was expecting it to "just work" (as jquery-rails does - //= require jquery), so another option might be changing React::Rails::Railtie.

I think README file should specify that in order to use builtin version of React user has to add a line to config file.

After installing the gem I was expecting it to "just work" (as `jquery-rails` does - `//= require jquery`), so another option might be changing `React::Rails::Railtie`.
@zpao
Copy link
Member

zpao commented Aug 20, 2013

Yea. I mentioned this somewhere (may have been in the React repo), but I thought about making it so that we do exactly what jquery-rails does, and we use the unminified in the development, test and minified in production environment. Or maybe just use those as defaults but allow config overrides. Let me know if you think this would be a better experience. You could work on it 😉

Regardless, this does clear it up. And I see you've signed the CLA already so I'll merge this in. Thanks a lot!

zpao added a commit that referenced this pull request Aug 20, 2013
Update usage instructions
@zpao zpao merged commit 34f7ce3 into reactjs:master Aug 20, 2013
@frantic frantic deleted the patch-1 branch August 21, 2013 09:51
@frantic
Copy link
Contributor Author

frantic commented Aug 21, 2013

Rails is always about convention over configuration, so providing default values with ability to override sound like a good choice. I'll send another PR a bit later. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants